[GH-ISSUE #27] DNS/IP results don t work #129

Closed
opened 2026-03-01 17:37:43 +03:00 by kerem · 4 comments
Owner

Originally created by @Andrejki on GitHub (Aug 16, 2022).
Original GitHub issue: https://github.com/alpkeskin/mosint/issues/27

Hi, thanks for the solution, but it is not good as it could be, apart from the DNS/IP showing always the same result.
Best regards

Originally created by @Andrejki on GitHub (Aug 16, 2022). Original GitHub issue: https://github.com/alpkeskin/mosint/issues/27 Hi, thanks for the solution, but it is not good as it could be, apart from the DNS/IP showing always the same result. Best regards
kerem closed this issue 2026-03-01 17:37:43 +03:00
Author
Owner

@calganaygun commented on GitHub (Aug 17, 2022):

Can you share examples of that issue, that could be used for reproducing? I am not able to find the same results for different domains.

<!-- gh-comment-id:1218269027 --> @calganaygun commented on GitHub (Aug 17, 2022): Can you share examples of that issue, that could be used for reproducing? I am not able to find the same results for different domains.
Author
Owner

@Andrejki commented on GitHub (Aug 22, 2022):

Hi. First example:

IP | 2a00:1450:4001:829::2005 |
| IP | 142.250.184.229 |
| NS | ns1.google.com. |
| NS | ns3.google.com. |
| NS | ns2.google.com. |
| NS | ns4.google.com. |
| MX | gmail-smtp-in.l.google.com. |
| MX | alt1.gmail-smtp-in.l.google.com. |
| MX | alt2.gmail-smtp-in.l.google.com. |
| MX | alt3.gmail-smtp-in.l.google.com. |
| MX | alt4.gmail-smtp-in.l.google.com. |
| TXT | v=spf1 |
| | redirect=_spf.google.com |
| TXT | globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8=

Second example:
| IP | 2a00:1450:4001:80b::2005 |
| IP | 142.250.184.229 |
| NS | ns4.google.com. |
| NS | ns2.google.com. |
| NS | ns3.google.com. |
| NS | ns1.google.com. |
| MX | gmail-smtp-in.l.google.com. |
| MX | alt1.gmail-smtp-in.l.google.com. |
| MX | alt2.gmail-smtp-in.l.google.com. |
| MX | alt3.gmail-smtp-in.l.google.com. |
| MX | alt4.gmail-smtp-in.l.google.com. |
| TXT | globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8= |
| TXT | v=spf1 |
| | redirect=_spf.google.com

If I run the thrd example with ofc the third different email address, I d get New York as I remember.
Best

<!-- gh-comment-id:1222419460 --> @Andrejki commented on GitHub (Aug 22, 2022): Hi. First example: IP | 2a00:1450:4001:829::2005 | | IP | 142.250.184.229 | | NS | ns1.google.com. | | NS | ns3.google.com. | | NS | ns2.google.com. | | NS | ns4.google.com. | | MX | gmail-smtp-in.l.google.com. | | MX | alt1.gmail-smtp-in.l.google.com. | | MX | alt2.gmail-smtp-in.l.google.com. | | MX | alt3.gmail-smtp-in.l.google.com. | | MX | alt4.gmail-smtp-in.l.google.com. | | TXT | v=spf1 | | | redirect=_spf.google.com | | TXT | globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8= Second example: | IP | 2a00:1450:4001:80b::2005 | | IP | 142.250.184.229 | | NS | ns4.google.com. | | NS | ns2.google.com. | | NS | ns3.google.com. | | NS | ns1.google.com. | | MX | gmail-smtp-in.l.google.com. | | MX | alt1.gmail-smtp-in.l.google.com. | | MX | alt2.gmail-smtp-in.l.google.com. | | MX | alt3.gmail-smtp-in.l.google.com. | | MX | alt4.gmail-smtp-in.l.google.com. | | TXT | globalsign-smime-dv=CDYX+XFHUw2wml6/Gb8+59BsH31KzUr6c1l2BPvqKX8= | | TXT | v=spf1 | | | redirect=_spf.google.com If I run the thrd example with ofc the third different email address, I d get New York as I remember. Best
Author
Owner

@calganaygun commented on GitHub (Aug 23, 2022):

I think you are testing Gmail/Google Workspace mail addresses. Since you analyze the same mail servers (Gmail in these examples) it is expected to find the same IP addresses. There are no bugs.

I would like to point out that DNS/IP resolution is related to the mail server's IP address, not the user's.

<!-- gh-comment-id:1223843944 --> @calganaygun commented on GitHub (Aug 23, 2022): I think you are testing Gmail/Google Workspace mail addresses. Since you analyze the same mail servers (Gmail in these examples) it is expected to find the same IP addresses. There are no bugs. I would like to point out that DNS/IP resolution is related to the mail server's IP address, not the user's.
Author
Owner

@Andrejki commented on GitHub (Sep 22, 2022):

Thanks, but you should have wrote that is related to user's IP address, not mail server's.
Cheers and all the best.
Thanks for building the tool.

<!-- gh-comment-id:1254513790 --> @Andrejki commented on GitHub (Sep 22, 2022): Thanks, but you should have wrote that is related to user's IP address, not mail server's. Cheers and all the best. Thanks for building the tool.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mosint#129
No description provided.