starred/mosint
1
0
Fork 0
mirror of https://github.com/alpkeskin/mosint.git synced 2026-04-26 19:45:54 +03:00
Code Issues 52 Projects Releases 5 Packages Wiki Activity

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

New issue
Closed
opened 2026-03-01 14:35:45 +03:00 by kerem · 4 comments
kerem commented 2026-03-01 14:35:45 +03:00
Owner
Copy link

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 14:35:45 +03:00
kerem commented 2026-03-01 14:35:46 +03:00
Author
Owner
Copy link

@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.
kerem commented 2026-03-01 14:35:46 +03:00
Author
Owner
Copy link

@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
kerem commented 2026-03-01 14:35:46 +03:00
Author
Owner
Copy link

@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.
kerem commented 2026-03-01 14:35:46 +03:00
Author
Owner
Copy link

@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 Branch/Tag specified
Branches Tags
master
v3.0.0
v2.3.1
v.2.3
v.2
v.14
v1.3
v1.2
v1.1
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
duplicate
enhancement
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#24
No description provided.