IPv4 address
40.70.158.182
Last fetched
40.70.158.182 is announced in 40.68.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation and geolocates to US. 40.70.158.182 is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- no-data
Nutrition Label
Attribution
- Announced prefix
- 40.68.0.0/14
- Announcing network
- MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation
- RIR-registered prefix
- 40.64.0.0/13
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- cpanel.recallhealth.ai
- mail.recallhealth.ai
- webdisk.recallhealth.ai
- www.recallhealth.ai
- ederm.co
- wildcard.ederm.co
- edermsys.com
- wildcard.edermsys.com
- edermsystems.com
- az-apps02.edermsystems.com
- betaweb.edermsystems.com
- support1.edermsystems.com
- wildcard.edermsystems.com
- www.edermsystems.com
- ederm.io
- beta-alpha.ederm.io
- beta-api.ederm.io
- beta-edermx.ederm.io
- beta-patient-portal.ederm.io
- beta-patient-registration.ederm.io
- beta-patient-scheduling.ederm.io
- beta-patient-telederm.ederm.io
- beta-portal.ederm.io
- beta-ps.ederm.io
- betapaymyderm.ederm.io
- migration-api.ederm.io
- migration-edermx.ederm.io
- staging-alpha.ederm.io
- staging-api.ederm.io
- staging-edermx.ederm.io
- staging-patient-portal.ederm.io
- staging-patient-registration.ederm.io
- staging-patient-scheduling.ederm.io
- staging-patient-telederm.ederm.io
- staging-paymyderm.ederm.io
- staging-portal.ederm.io
- staging-ps.ederm.io
- edermsystems.net
- bitwarden.edermsystems.net
- wildcard.edermsystems.net
Geographic detail
- City
- Boydton, US
- Country
- US
Threat-feed evidence
History
Related pages
Pivot from 40.70.158.182 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "40.70.158.182"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.