IPv4 address
207.199.149.248
Last fetched
207.199.149.248 is announced in 207.199.149.0/24 by MOD-EU - Mod Mission Critical LLC and geolocates to FR. 207.199.149.248 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
- 207.199.149.0/24
- Announcing network
- MOD-EU - Mod Mission Critical LLC
- RIR-registered prefix
- 207.199.128.0/18
- RPKI
- not-found
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
- w8n1.par.idrivee2-18.com
- h7y2.par.idrivee2-20.com
- b7j4.par.idrivee2-21.com
- t1f1.par.idrivee2-22.com
- a2q8.par.idrivee2-24.com
- f2g3.par.idrivee2-24.com
- g3d2.par.idrivee2-26.com
- l5e7.par.idrivee2-26.com
- n5h6.par.idrivee2-26.com
- s8q7.par.idrivee2-26.com
- w8e1.par.idrivee2-26.com
- c2i2.par.idrivee2-27.com
- a5k6.par.idrivee2-34.com
- g0q0.par.idrivee2-34.com
- r8k1.par.idrivee2-34.com
- s2u1.par.idrivee2-34.com
- q1g7.par.idrivee2-35.com
- h4a2.par.idrivee2-36.com
- f4a6.par.idrivee2-38.com
- o5i0.par.idrivee2-38.com
- w8a5.par.idrivee2-38.com
- b2r3.par.idrivee2-39.com
- e5m4.par.idrivee2-40.com
- f6f4.par.idrivee2-40.com
- x8y0.par.idrivee2-40.com
- n5q6.par.idrivee2-41.com
- t8d8.par.idrivee2-41.com
- y5r7.par.idrivee2-42.com
- d2n2.par.idrivee2-43.com
- m4q4.par.idrivee2-43.com
- n4k2.par.idrivee2-43.com
- a4k5.par.idrivee2-44.com
- c2n1.par.idrivee2-44.com
- c2v0.par.idrivee2-44.com
- m8l1.par.idrivee2-45.com
- s7o2.par.idrivee2-45.com
- l7w6.par.idrivee2-46.com
- g2p7.c1.e2-8.dev
Geographic detail
- City
- Saint-Denis, FR
- Country
- FR
- Dominant city of the prefix
- Saint-Denis, FR
Threat-feed evidence
History
Related pages
Pivot from 207.199.149.248 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: "207.199.149.248"})
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.